Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eb5b0ef1e7ff82e6b7625b1264357c7718994810d13d8b4bcf2f9852a95b325

Tx prefix hash: f0725f58d1a6a06700543fc69b3c9dc4eb8529459c56eb0b1d5875ebca80f086
Tx public key: 31979646d1e060213fa4625e3c4d8c2d12e9c4a22f04492073d287d07b120f07
Timestamp: 1738551715 Timestamp [UCT]: 2025-02-03 03:01:55 Age [y:d:h:m:s]: 00:298:04:23:27
Block: 1210915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210900 RingCT/type: yes/0
Extra: 0131979646d1e060213fa4625e3c4d8c2d12e9c4a22f04492073d287d07b120f070211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1b7b0d448955d164c92ab606c54d1ec2802ed309067b8a83f301c6839a6428a 0.600000000000 1697670 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": 1210925, "vin": [ { "gen": { "height": 1210915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1b7b0d448955d164c92ab606c54d1ec2802ed309067b8a83f301c6839a6428a" } } ], "extra": [ 1, 49, 151, 150, 70, 209, 224, 96, 33, 63, 164, 98, 94, 60, 77, 140, 45, 18, 233, 196, 162, 47, 4, 73, 32, 115, 210, 135, 208, 123, 18, 15, 7, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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