Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42cb4b202902cc949877e0daf092253203d5df8ae9c3048861f423a942a45b6b

Tx prefix hash: 2947e41854e57b945940417596f6bd4a78186673f7057bf462df1097d821edce
Tx public key: ca29803ef17bd6d13d4a9c36e90e523c22c01cc8dcbd9d7d65f67b45bfb73f95
Timestamp: 1722704722 Timestamp [UCT]: 2024-08-03 17:05:22 Age [y:d:h:m:s]: 00:256:18:37:17
Block: 1079976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183421 RingCT/type: yes/0
Extra: 01ca29803ef17bd6d13d4a9c36e90e523c22c01cc8dcbd9d7d65f67b45bfb73f9502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4631bcc19a25d2940a6d9963e545fee655c6516f4f96db261982f11c25ea19d4 0.600000000000 1553157 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": 1079986, "vin": [ { "gen": { "height": 1079976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4631bcc19a25d2940a6d9963e545fee655c6516f4f96db261982f11c25ea19d4" } } ], "extra": [ 1, 202, 41, 128, 62, 241, 123, 214, 209, 61, 74, 156, 54, 233, 14, 82, 60, 34, 192, 28, 200, 220, 189, 157, 125, 101, 246, 123, 69, 191, 183, 63, 149, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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