Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db3a39cc49ec619c5546142a35293a3e5134f471c3b294f0eb3aa4a052ac9c97

Tx prefix hash: 6741120781a4cc7ca1653a324528ce9a713c51c236f90ed65c82ee4a2ec2d692
Tx public key: 174a89e4e073004f7dc56f70092f85e5bba60a0c000c9229bfd2ed24d1cd3498
Timestamp: 1712388180 Timestamp [UCT]: 2024-04-06 07:23:00 Age [y:d:h:m:s]: 01:020:00:09:02
Block: 994421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275292 RingCT/type: yes/0
Extra: 01174a89e4e073004f7dc56f70092f85e5bba60a0c000c9229bfd2ed24d1cd349802110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0bd8edc6e29e03dd8539d4103ee8876fc44442d8dd7a06b5a90a9f463313653 0.600000000000 1454823 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": 994431, "vin": [ { "gen": { "height": 994421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0bd8edc6e29e03dd8539d4103ee8876fc44442d8dd7a06b5a90a9f463313653" } } ], "extra": [ 1, 23, 74, 137, 228, 224, 115, 0, 79, 125, 197, 111, 112, 9, 47, 133, 229, 187, 166, 10, 12, 0, 12, 146, 41, 191, 210, 237, 36, 209, 205, 52, 152, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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