Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 787bf80e92a326e656f2687b8f402154ab51306ea69f99c265e4d5f1d176e873

Tx prefix hash: 5a926f1d7d992b0aeddf3f0e1c4d3c8cfd9ed3e2acbd2b96eb954acc7549b92c
Tx public key: 60088d5ecd3c1a97b514fd66e88d7f03ba139d76b10a93bd596b25aa11f4b941
Timestamp: 1716057030 Timestamp [UCT]: 2024-05-18 18:30:30 Age [y:d:h:m:s]: 01:028:09:51:58
Block: 1024862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281140 RingCT/type: yes/0
Extra: 0160088d5ecd3c1a97b514fd66e88d7f03ba139d76b10a93bd596b25aa11f4b94102110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44bbc143e5053c26c9896a4c8374fd2242687ec594fb396c68e6adf31541c0e7 0.600000000000 1490943 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": 1024872, "vin": [ { "gen": { "height": 1024862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44bbc143e5053c26c9896a4c8374fd2242687ec594fb396c68e6adf31541c0e7" } } ], "extra": [ 1, 96, 8, 141, 94, 205, 60, 26, 151, 181, 20, 253, 102, 232, 141, 127, 3, 186, 19, 157, 118, 177, 10, 147, 189, 89, 107, 37, 170, 17, 244, 185, 65, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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