Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b47a70cac1e4c274daf82d52a19a342d8dc655643abef90028a195b4737f1210

Tx prefix hash: 84876a569271fa1506477620bf8ecdf2080dadb68d62f160b626f3b3160bd1d2
Tx public key: 0279af111ea5cb1ea7a73c0b0b7a25c6662462e8ac8c189679839f41e1b1f3e0
Timestamp: 1730974875 Timestamp [UCT]: 2024-11-07 10:21:15 Age [y:d:h:m:s]: 00:136:13:37:55
Block: 1148455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97420 RingCT/type: yes/0
Extra: 010279af111ea5cb1ea7a73c0b0b7a25c6662462e8ac8c189679839f41e1b1f3e00211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e7c502e0fc3414123e0907010a3797adac932ee07369b9777f4092d23bd697f 0.600000000000 1633302 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": 1148465, "vin": [ { "gen": { "height": 1148455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e7c502e0fc3414123e0907010a3797adac932ee07369b9777f4092d23bd697f" } } ], "extra": [ 1, 2, 121, 175, 17, 30, 165, 203, 30, 167, 167, 60, 11, 11, 122, 37, 198, 102, 36, 98, 232, 172, 140, 24, 150, 121, 131, 159, 65, 225, 177, 243, 224, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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