Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 721ecca5feb32272c81ac11d9da020407d3e53d093aa916c7d4444b55b1b7eee

Tx prefix hash: 6100c752cf2ae1a0bb514d7b194a85884e9e67661460313de1e86abc28cf88d8
Tx public key: 0debce2c4c2561280c481b59bba548479ab72a3283e5e85ba62a4143890a6261
Timestamp: 1701849236 Timestamp [UCT]: 2023-12-06 07:53:56 Age [y:d:h:m:s]: 01:122:03:01:01
Block: 907078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348430 RingCT/type: yes/0
Extra: 010debce2c4c2561280c481b59bba548479ab72a3283e5e85ba62a4143890a6261021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.606001938000 dcy

stealth address amount amount idx
00: a53be11aa66906de3e8f546c7f017e9f6a665e1d7f9bedba8e9a8cceb17346ba 0.606001938000 1364043 of 0

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": 907088, "vin": [ { "gen": { "height": 907078 } } ], "vout": [ { "amount": 606001938, "target": { "key": "a53be11aa66906de3e8f546c7f017e9f6a665e1d7f9bedba8e9a8cceb17346ba" } } ], "extra": [ 1, 13, 235, 206, 44, 76, 37, 97, 40, 12, 72, 27, 89, 187, 165, 72, 71, 154, 183, 42, 50, 131, 229, 232, 91, 166, 42, 65, 67, 137, 10, 98, 97, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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