Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73cfa2c3dbd4035f71ce4f89151bdfc038420e2afeaa4dd85143bd15d8da429

Tx prefix hash: 5dd3ba7d289083b724a12d7caafa90a5c13fe236f33d3352cb730ed83eb2aeca
Tx public key: 1c0dce63ed1e35d2a088d53e7b71419571fd938e824019def2a17e3b4896a92f
Timestamp: 1712826252 Timestamp [UCT]: 2024-04-11 09:04:12 Age [y:d:h:m:s]: 01:047:18:42:28
Block: 998054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295165 RingCT/type: yes/0
Extra: 011c0dce63ed1e35d2a088d53e7b71419571fd938e824019def2a17e3b4896a92f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f8f4502e4de74e25f410fa0fd07165c9a679a18962507e5e8d47fd715e1aae2 0.600000000000 1458488 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": 998064, "vin": [ { "gen": { "height": 998054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f8f4502e4de74e25f410fa0fd07165c9a679a18962507e5e8d47fd715e1aae2" } } ], "extra": [ 1, 28, 13, 206, 99, 237, 30, 53, 210, 160, 136, 213, 62, 123, 113, 65, 149, 113, 253, 147, 142, 130, 64, 25, 222, 242, 161, 126, 59, 72, 150, 169, 47, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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