Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d003ae1ddbf48d58bd0269bc26a35b1061a45a7a34a6fccb81268762c570a76a

Tx prefix hash: 84326e61b68a967bfec5aa05d609a1e4999b0ebcb52a516848fe01a9d6531377
Tx public key: 4f47c094688aba1cfc7903a64e3049686547e35b2ef24c2f1b919b65e51b9859
Timestamp: 1725185364 Timestamp [UCT]: 2024-09-01 10:09:24 Age [y:d:h:m:s]: 00:242:12:24:47
Block: 1100543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173192 RingCT/type: yes/0
Extra: 014f47c094688aba1cfc7903a64e3049686547e35b2ef24c2f1b919b65e51b9859021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3f8808c11c9ff6a4f9dfd55447e7405555a89e50612c56bbc36bcdbc618b9cc 0.600000000000 1576522 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": 1100553, "vin": [ { "gen": { "height": 1100543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3f8808c11c9ff6a4f9dfd55447e7405555a89e50612c56bbc36bcdbc618b9cc" } } ], "extra": [ 1, 79, 71, 192, 148, 104, 138, 186, 28, 252, 121, 3, 166, 78, 48, 73, 104, 101, 71, 227, 91, 46, 242, 76, 47, 27, 145, 155, 101, 229, 27, 152, 89, 2, 17, 0, 0, 0, 1, 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