Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 088c6b531349380875f06998f967e0c63c78447905bdb0d4915efb999f888266

Tx prefix hash: 629c57b69abcb80ca09e8b75000701e436aa86f8fe3314141c6655da89553ad0
Tx public key: 56045c00a94d2f3ebfeae86ce0e234dc7b4c82b3964fba8d3144a22a6f82a584
Timestamp: 1736496750 Timestamp [UCT]: 2025-01-10 08:12:30 Age [y:d:h:m:s]: 00:088:12:06:42
Block: 1194173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63034 RingCT/type: yes/0
Extra: 0156045c00a94d2f3ebfeae86ce0e234dc7b4c82b3964fba8d3144a22a6f82a584021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a66e86c1504c6e6853e104a73de610a6119bc5dc844e0ea905fe756035f4e5e 0.600000000000 1680740 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": 1194183, "vin": [ { "gen": { "height": 1194173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a66e86c1504c6e6853e104a73de610a6119bc5dc844e0ea905fe756035f4e5e" } } ], "extra": [ 1, 86, 4, 92, 0, 169, 77, 47, 62, 191, 234, 232, 108, 224, 226, 52, 220, 123, 76, 130, 179, 150, 79, 186, 141, 49, 68, 162, 42, 111, 130, 165, 132, 2, 17, 0, 0, 0, 1, 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