Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d51e751a7d415df7d234778aa85fa86c359818aff7efb84205c729bf01f2729c

Tx prefix hash: a49f38516b983b4e27e014d41d3a25c858722590c963b98f312483e9cc0cef24
Tx public key: ea9093b54550a564d2426cf5dd40606086c9f953ce3f7bd7abbd4e3f64a21f25
Timestamp: 1709216157 Timestamp [UCT]: 2024-02-29 14:15:57 Age [y:d:h:m:s]: 01:042:06:59:16
Block: 968160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291238 RingCT/type: yes/0
Extra: 01ea9093b54550a564d2426cf5dd40606086c9f953ce3f7bd7abbd4e3f64a21f2502110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a1a7665ba9af86bf0234995c3a584e841f9be78b6b3bb60038a25906229691a 0.600000000000 1427959 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": 968170, "vin": [ { "gen": { "height": 968160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a1a7665ba9af86bf0234995c3a584e841f9be78b6b3bb60038a25906229691a" } } ], "extra": [ 1, 234, 144, 147, 181, 69, 80, 165, 100, 210, 66, 108, 245, 221, 64, 96, 96, 134, 201, 249, 83, 206, 63, 123, 215, 171, 189, 78, 63, 100, 162, 31, 37, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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