Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5214ae24c8198addd49ea09f0ce9500ab3ab081e6be7e756185cfe127bff90a4

Tx prefix hash: 476e7d17f2202c79b4e9dfaf20596147fef3c88db529536017f8d564d2f22e61
Tx public key: 85578f90f1e3c5cedd46dcb720b0e3d62ab1075fed2204f5c3422aebc08532b7
Timestamp: 1671359230 Timestamp [UCT]: 2022-12-18 10:27:10 Age [y:d:h:m:s]: 02:031:12:59:15
Block: 655190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544450 RingCT/type: yes/0
Extra: 0185578f90f1e3c5cedd46dcb720b0e3d62ab1075fed2204f5c3422aebc08532b70211000000037e406890000000000000000000

1 output(s) for total of 4.140793059000 dcy

stealth address amount amount idx
00: f9e0a1b17fa75e54a7bfe84e0c3c984186455149747e9342c0863a42c81ce674 4.140793059000 1095737 of 0

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": 655200, "vin": [ { "gen": { "height": 655190 } } ], "vout": [ { "amount": 4140793059, "target": { "key": "f9e0a1b17fa75e54a7bfe84e0c3c984186455149747e9342c0863a42c81ce674" } } ], "extra": [ 1, 133, 87, 143, 144, 241, 227, 197, 206, 221, 70, 220, 183, 32, 176, 227, 214, 42, 177, 7, 95, 237, 34, 4, 245, 195, 66, 42, 235, 192, 133, 50, 183, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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