Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb6263a29d7062a0c5dc0ce3f3f60c572f0878c650f29307226cf6f66890dac8

Tx prefix hash: 70f0983e7948bbd2f7653794026a1a4ddb1cae9d928a5b1db3064aedf29e0fea
Tx public key: 53e0789e98323bb8d2cd23df6487fd7b84b51245aba07245e4b0e9c965c5175e
Timestamp: 1736858565 Timestamp [UCT]: 2025-01-14 12:42:45 Age [y:d:h:m:s]: 00:307:00:32:54
Block: 1197180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216934 RingCT/type: yes/0
Extra: 0153e0789e98323bb8d2cd23df6487fd7b84b51245aba07245e4b0e9c965c5175e02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ce2ad88df3d5f78fd85e14e1ef62b24af1ec44761d218f51940aed98b8109cc 0.600000000000 1683787 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": 1197190, "vin": [ { "gen": { "height": 1197180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ce2ad88df3d5f78fd85e14e1ef62b24af1ec44761d218f51940aed98b8109cc" } } ], "extra": [ 1, 83, 224, 120, 158, 152, 50, 59, 184, 210, 205, 35, 223, 100, 135, 253, 123, 132, 181, 18, 69, 171, 160, 114, 69, 228, 176, 233, 201, 101, 197, 23, 94, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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