Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab7260f75b8ec5099efd8bbdaa49dc52be9a365dfd01ca9e1e018036f23ff95

Tx prefix hash: add40d7fd62eb9cf88e73818c5de642614d4aa2bea34f4e58785d945080d83ac
Tx public key: 51e89ded2003f0bfe58c5b5632c2cc14ea0602766df948e287c701a460924f69
Timestamp: 1725680382 Timestamp [UCT]: 2024-09-07 03:39:42 Age [y:d:h:m:s]: 00:145:11:09:32
Block: 1104642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103779 RingCT/type: yes/0
Extra: 0151e89ded2003f0bfe58c5b5632c2cc14ea0602766df948e287c701a460924f6902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fdb4b263577f7eb064a1555e01e2d4e3ec46689fe4d6b3c41852f8775d0cfce 0.600000000000 1581863 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": 1104652, "vin": [ { "gen": { "height": 1104642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fdb4b263577f7eb064a1555e01e2d4e3ec46689fe4d6b3c41852f8775d0cfce" } } ], "extra": [ 1, 81, 232, 157, 237, 32, 3, 240, 191, 229, 140, 91, 86, 50, 194, 204, 20, 234, 6, 2, 118, 109, 249, 72, 226, 135, 199, 1, 164, 96, 146, 79, 105, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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