Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3f8039189d8cdcde11d30e4bad1f6c7a7f8a6f55a404b7d8955fce2ba4babb

Tx prefix hash: b9639669794655913840bcfa7bfd914576864b15b192a47c7aced0ad3b69403c
Tx public key: d09c81af67facfc597a7327945e9a196f14fb6235ef796b7ee4c747d05278399
Timestamp: 1673218023 Timestamp [UCT]: 2023-01-08 22:47:03 Age [y:d:h:m:s]: 02:091:22:24:28
Block: 670559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587397 RingCT/type: yes/0
Extra: 01d09c81af67facfc597a7327945e9a196f14fb6235ef796b7ee4c747d05278399021100000008faf35c9c000000000000000000

1 output(s) for total of 3.682643062000 dcy

stealth address amount amount idx
00: 7b397592c80f8c4e04e5fa93a6bd59687d30c67d11f0ac0abd3f5f48c0408393 3.682643062000 1111970 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": 670569, "vin": [ { "gen": { "height": 670559 } } ], "vout": [ { "amount": 3682643062, "target": { "key": "7b397592c80f8c4e04e5fa93a6bd59687d30c67d11f0ac0abd3f5f48c0408393" } } ], "extra": [ 1, 208, 156, 129, 175, 103, 250, 207, 197, 151, 167, 50, 121, 69, 233, 161, 150, 241, 79, 182, 35, 94, 247, 150, 183, 238, 76, 116, 125, 5, 39, 131, 153, 2, 17, 0, 0, 0, 8, 250, 243, 92, 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