Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0226fd2e3418f2c1dbffb8bedeba28387c113093e6bcf460470feefae522aab4

Tx prefix hash: 7ad535bd50ee3b8f5f7b5e8e4c523a2bab7027851122217b5d52d2657ed469a3
Tx public key: 0770cad3de7af476b3ad8d71b15cb86891c5ad5b8e3138d939e9c99123d28e64
Timestamp: 1714263931 Timestamp [UCT]: 2024-04-28 00:25:31 Age [y:d:h:m:s]: 00:256:07:12:04
Block: 1009996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183456 RingCT/type: yes/0
Extra: 010770cad3de7af476b3ad8d71b15cb86891c5ad5b8e3138d939e9c99123d28e6402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0417e19efcbb7b518d195ce10632e1fb5fa6527941b5bf2573b17e7ec40cd0fa 0.600000000000 1471826 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": 1010006, "vin": [ { "gen": { "height": 1009996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0417e19efcbb7b518d195ce10632e1fb5fa6527941b5bf2573b17e7ec40cd0fa" } } ], "extra": [ 1, 7, 112, 202, 211, 222, 122, 244, 118, 179, 173, 141, 113, 177, 92, 184, 104, 145, 197, 173, 91, 142, 49, 56, 217, 57, 233, 201, 145, 35, 210, 142, 100, 2, 17, 0, 0, 0, 1, 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