Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22e72532e8432e09756ff91b8694914ed30dd06ceca0cb47d1bce60be5371371

Tx prefix hash: e1f23790603252fc3ddbca6b61a6f4c09f7c58e7001353cef42fa950df934fd3
Tx public key: 54304fcb3e335eb5dcb1d3388d8b2d50459f414462da29a1c1a6edc6e53700f0
Timestamp: 1710033680 Timestamp [UCT]: 2024-03-10 01:21:20 Age [y:d:h:m:s]: 00:350:06:06:18
Block: 974939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250399 RingCT/type: yes/0
Extra: 0154304fcb3e335eb5dcb1d3388d8b2d50459f414462da29a1c1a6edc6e53700f002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb43d865a44603aa61dbdf09aae63e76e9a63416121dc5ee5fe1ab01a14740a2 0.600000000000 1434906 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": 974949, "vin": [ { "gen": { "height": 974939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb43d865a44603aa61dbdf09aae63e76e9a63416121dc5ee5fe1ab01a14740a2" } } ], "extra": [ 1, 84, 48, 79, 203, 62, 51, 94, 181, 220, 177, 211, 56, 141, 139, 45, 80, 69, 159, 65, 68, 98, 218, 41, 161, 193, 166, 237, 198, 229, 55, 0, 240, 2, 17, 0, 0, 0, 3, 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