Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0fde9918f06288966b609f2b7f296ade4417e7d64302594df9fedd31b6e5f6

Tx prefix hash: 03d253874eb49c0774fa9bff3fd5ebb9a52993b37fece0ad846c8c7045b89a7d
Tx public key: 56a58c678f65952d8c606cc47f3487c43a9cf23b4c120b23dcdcb818bdfb54be
Timestamp: 1733381219 Timestamp [UCT]: 2024-12-05 06:46:59 Age [y:d:h:m:s]: 00:124:06:35:50
Block: 1168390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88610 RingCT/type: yes/0
Extra: 0156a58c678f65952d8c606cc47f3487c43a9cf23b4c120b23dcdcb818bdfb54be021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 362f89188a71bdd5dd9bc2b3b2a5c99920c2a8987985d3aa216773dd687c407e 0.600000000000 1654099 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": 1168400, "vin": [ { "gen": { "height": 1168390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "362f89188a71bdd5dd9bc2b3b2a5c99920c2a8987985d3aa216773dd687c407e" } } ], "extra": [ 1, 86, 165, 140, 103, 143, 101, 149, 45, 140, 96, 108, 196, 127, 52, 135, 196, 58, 156, 242, 59, 76, 18, 11, 35, 220, 220, 184, 24, 189, 251, 84, 190, 2, 17, 0, 0, 0, 7, 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