Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44badbe374c9e4e39ede061f012b76433da5f190814901811c40a5baf12af217

Tx prefix hash: 6839525a32371ae2d7f62a0568d8271fb15cacbfc53be1ca91d8577bdcdc3b9c
Tx public key: fae4aca2ef79386a0f8b811aa4ceb9dbf94d18e92bf06996aca0a531f5a6d58b
Timestamp: 1730387638 Timestamp [UCT]: 2024-10-31 15:13:58 Age [y:d:h:m:s]: 00:139:15:36:35
Block: 1143591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99654 RingCT/type: yes/0
Extra: 01fae4aca2ef79386a0f8b811aa4ceb9dbf94d18e92bf06996aca0a531f5a6d58b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0bf1304f8d559c7763214fff408fa561e5d97142a0e5dee2025c58fe0c2b8d1 0.600000000000 1627516 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": 1143601, "vin": [ { "gen": { "height": 1143591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0bf1304f8d559c7763214fff408fa561e5d97142a0e5dee2025c58fe0c2b8d1" } } ], "extra": [ 1, 250, 228, 172, 162, 239, 121, 56, 106, 15, 139, 129, 26, 164, 206, 185, 219, 249, 77, 24, 233, 43, 240, 105, 150, 172, 160, 165, 49, 245, 166, 213, 139, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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