Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da221c848f7cebff68e80aee7a4ff510861ab5179c0b2a85d4b377925f53cd0

Tx prefix hash: e1f25cea581921228f18a33b4e0ca200e599107ddc68e1328d82b81102f1bbd4
Tx public key: 2b3464e5269154536a455b55ab0f164a0446d9a2f6bebc63a59177ad1f6d47e6
Timestamp: 1723621487 Timestamp [UCT]: 2024-08-14 07:44:47 Age [y:d:h:m:s]: 00:193:05:44:29
Block: 1087579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137943 RingCT/type: yes/0
Extra: 012b3464e5269154536a455b55ab0f164a0446d9a2f6bebc63a59177ad1f6d47e6021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43952458fe26f76e3c26e68c5e321bef0081569783eb248d2ae0136d6fb38a4f 0.600000000000 1562188 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": 1087589, "vin": [ { "gen": { "height": 1087579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43952458fe26f76e3c26e68c5e321bef0081569783eb248d2ae0136d6fb38a4f" } } ], "extra": [ 1, 43, 52, 100, 229, 38, 145, 84, 83, 106, 69, 91, 85, 171, 15, 22, 74, 4, 70, 217, 162, 246, 190, 188, 99, 165, 145, 119, 173, 31, 109, 71, 230, 2, 17, 0, 0, 0, 2, 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