Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c91ad6f5f41fac033e96698c8a7c4da9559063bc8930948531f4563a1644ac3c

Tx prefix hash: 573ddbd7be59cbb7af61f0cb21bfbd5cf2d14315607992fd939973ef2d7311fc
Tx public key: bc6559dbf186b4f4b9dee2bbdb462669fb898cd58717683d4b178195e510d34b
Timestamp: 1736106346 Timestamp [UCT]: 2025-01-05 19:45:46 Age [y:d:h:m:s]: 00:085:00:57:37
Block: 1190951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60558 RingCT/type: yes/0
Extra: 01bc6559dbf186b4f4b9dee2bbdb462669fb898cd58717683d4b178195e510d34b02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d628e7e1604d98c7f9080906d3fa8c5b16d81dee7bb1b74d52627430d47e0d2e 0.600000000000 1677474 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": 1190961, "vin": [ { "gen": { "height": 1190951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d628e7e1604d98c7f9080906d3fa8c5b16d81dee7bb1b74d52627430d47e0d2e" } } ], "extra": [ 1, 188, 101, 89, 219, 241, 134, 180, 244, 185, 222, 226, 187, 219, 70, 38, 105, 251, 137, 140, 213, 135, 23, 104, 61, 75, 23, 129, 149, 229, 16, 211, 75, 2, 17, 0, 0, 0, 11, 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