Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0604675b98f1daa9b72143e2d6a9a0afcaa88c4fcf8511005ac0ac51146a758b

Tx prefix hash: c89af9dd2db7c91c2b30d0fb2d0f52a146ee8f4ef913a1a77efe65ad3e1f9bbb
Tx public key: af2dffa9b3a2f3f6c3e85b66962e60771f521e5a4177e90322eaf59ab4c2324e
Timestamp: 1711670327 Timestamp [UCT]: 2024-03-28 23:58:47 Age [y:d:h:m:s]: 00:333:05:53:05
Block: 988516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238218 RingCT/type: yes/0
Extra: 01af2dffa9b3a2f3f6c3e85b66962e60771f521e5a4177e90322eaf59ab4c2324e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a19ffaa7141a64a1b3925432df9dad0f22a4bbc796123904b5d405d5647874b 0.600000000000 1448795 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": 988526, "vin": [ { "gen": { "height": 988516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a19ffaa7141a64a1b3925432df9dad0f22a4bbc796123904b5d405d5647874b" } } ], "extra": [ 1, 175, 45, 255, 169, 179, 162, 243, 246, 195, 232, 91, 102, 150, 46, 96, 119, 31, 82, 30, 90, 65, 119, 233, 3, 34, 234, 245, 154, 180, 194, 50, 78, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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