Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c2f94d06f561ee36e838ae7e7fd157b96180c67e11c042e929957d6fd8123ef

Tx prefix hash: cdbe6caf7f3304c96f13aec17adcb94eddc0546d53c1e934ceacb005e86edfb8
Tx public key: b88dc803189d7b6590afaa22f78b2c5648ef75220f0400f11c4063d9abcb1db3
Timestamp: 1730394157 Timestamp [UCT]: 2024-10-31 17:02:37 Age [y:d:h:m:s]: 00:081:20:47:27
Block: 1143648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58525 RingCT/type: yes/0
Extra: 01b88dc803189d7b6590afaa22f78b2c5648ef75220f0400f11c4063d9abcb1db3021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf812b06d38835d03d541265c865f2d7cf303234d6fe39424cafa315a221c14e 0.600000000000 1627589 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": 1143658, "vin": [ { "gen": { "height": 1143648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf812b06d38835d03d541265c865f2d7cf303234d6fe39424cafa315a221c14e" } } ], "extra": [ 1, 184, 141, 200, 3, 24, 157, 123, 101, 144, 175, 170, 34, 247, 139, 44, 86, 72, 239, 117, 34, 15, 4, 0, 241, 28, 64, 99, 217, 171, 203, 29, 179, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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