Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95930c393a35e8935c281bebc9b30b0d8d4022413296f6e4ec606f0b388fbff6

Tx prefix hash: 20d3d209e58cda11a3c3ef1cfbad7995c93535671932b75a202474c040191099
Tx public key: b1e3a2083c72438c7ff69d3b45c30910c947535468c0ac71ea2c23c208d50a49
Timestamp: 1735883281 Timestamp [UCT]: 2025-01-03 05:48:01 Age [y:d:h:m:s]: 00:170:14:15:51
Block: 1189114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121533 RingCT/type: yes/0
Extra: 01b1e3a2083c72438c7ff69d3b45c30910c947535468c0ac71ea2c23c208d50a49021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80db525d1169e1f8c548d94d67e3f55c729cc9cdcff8ec60f5caaf6acaad08ec 0.600000000000 1675619 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": 1189124, "vin": [ { "gen": { "height": 1189114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80db525d1169e1f8c548d94d67e3f55c729cc9cdcff8ec60f5caaf6acaad08ec" } } ], "extra": [ 1, 177, 227, 162, 8, 60, 114, 67, 140, 127, 246, 157, 59, 69, 195, 9, 16, 201, 71, 83, 84, 104, 192, 172, 113, 234, 44, 35, 194, 8, 213, 10, 73, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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