Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3db2e2e9ccc13400bcb6379798715d313d4ac56b782faca6507c57b9e5a34cb1

Tx prefix hash: 156f6b93ba99bdcc15099bd79f3af1d61c23247ea213e4f466b9c2ab48a139b8
Tx public key: 9764b6fa3747920c5d762e377ab56d915aeea7afd8374a31a659f70a6c2b08e9
Timestamp: 1707012665 Timestamp [UCT]: 2024-02-04 02:11:05 Age [y:d:h:m:s]: 01:277:21:41:27
Block: 949867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457406 RingCT/type: yes/0
Extra: 019764b6fa3747920c5d762e377ab56d915aeea7afd8374a31a659f70a6c2b08e902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbac840edc1456e0f72f792e8ef17e5c433f06612053569d846080d73bdb53be 0.600000000000 1408401 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": 949877, "vin": [ { "gen": { "height": 949867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbac840edc1456e0f72f792e8ef17e5c433f06612053569d846080d73bdb53be" } } ], "extra": [ 1, 151, 100, 182, 250, 55, 71, 146, 12, 93, 118, 46, 55, 122, 181, 109, 145, 90, 238, 167, 175, 216, 55, 74, 49, 166, 89, 247, 10, 108, 43, 8, 233, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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