Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 405eca867eebaf23086b210b1757a472be6c8d48c391c4d36cb87f0a7d089786

Tx prefix hash: 3b769e358c23f8540a6c8ef2b0f2a77e41ed96ebc55d835f7ec90410bd8e3ab3
Tx public key: 8afba10e25eb614041aef55d98cb4321e08bd4737e1ed549166bac7b050efb1e
Timestamp: 1702736420 Timestamp [UCT]: 2023-12-16 14:20:20 Age [y:d:h:m:s]: 01:150:05:54:09
Block: 914425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368549 RingCT/type: yes/0
Extra: 018afba10e25eb614041aef55d98cb4321e08bd4737e1ed549166bac7b050efb1e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0eab0ede9d0c654b9c808bdc37eb71e1406b5d6dd59e6ae2b5643a17c64a433 0.600000000000 1371741 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 914435, "vin": [ { "gen": { "height": 914425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0eab0ede9d0c654b9c808bdc37eb71e1406b5d6dd59e6ae2b5643a17c64a433" } } ], "extra": [ 1, 138, 251, 161, 14, 37, 235, 97, 64, 65, 174, 245, 93, 152, 203, 67, 33, 224, 139, 212, 115, 126, 30, 213, 73, 22, 107, 172, 123, 5, 14, 251, 30, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8