Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c040e835a31384f30f3a96dc89d5130e31e920eddae879a593546fe34c4fe485

Tx prefix hash: 0bdbe2a1fee5b14aa442f8f03da567d3d567289e9cef3d116f5aa3fc049a95df
Tx public key: 005d9d23c244182ce1886572a42a493cd9ff8df8540a78c818537ef7bcf53909
Timestamp: 1703063773 Timestamp [UCT]: 2023-12-20 09:16:13 Age [y:d:h:m:s]: 01:117:00:22:13
Block: 917147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344763 RingCT/type: yes/0
Extra: 01005d9d23c244182ce1886572a42a493cd9ff8df8540a78c818537ef7bcf53909021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 905b25350afd29c6685887aa5eb70e598fc1273c2c4dbdff4f3c4c16cf4b040a 0.600000000000 1374715 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": 917157, "vin": [ { "gen": { "height": 917147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "905b25350afd29c6685887aa5eb70e598fc1273c2c4dbdff4f3c4c16cf4b040a" } } ], "extra": [ 1, 0, 93, 157, 35, 194, 68, 24, 44, 225, 136, 101, 114, 164, 42, 73, 60, 217, 255, 141, 248, 84, 10, 120, 200, 24, 83, 126, 247, 188, 245, 57, 9, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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