Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 445cb3b699d758f6d775bf41c468871eba137befd9677afa2ad392e2b5d4ae47

Tx prefix hash: f71efb3f2ad27b26a3ff39367fcfaa666ca4f5f53069d41445d290d3c9677179
Tx public key: a510ae0229c8e095b1f3ae105b71aaf8b70c2ade8d997add087fe9d4d3ed7c9b
Timestamp: 1725586699 Timestamp [UCT]: 2024-09-06 01:38:19 Age [y:d:h:m:s]: 00:224:15:56:44
Block: 1103878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160417 RingCT/type: yes/0
Extra: 01a510ae0229c8e095b1f3ae105b71aaf8b70c2ade8d997add087fe9d4d3ed7c9b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8eb99f95c0dcba1365ffe5e6bd1a2fd2386fa236ec859e0dd66b4b0826c8b25 0.600000000000 1580875 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": 1103888, "vin": [ { "gen": { "height": 1103878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8eb99f95c0dcba1365ffe5e6bd1a2fd2386fa236ec859e0dd66b4b0826c8b25" } } ], "extra": [ 1, 165, 16, 174, 2, 41, 200, 224, 149, 177, 243, 174, 16, 91, 113, 170, 248, 183, 12, 42, 222, 141, 153, 122, 221, 8, 127, 233, 212, 211, 237, 124, 155, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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