Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc54e3936c6d9bfe5ec6005ddd10a662b2f1fdd8c82d82597e180365cfec7f06

Tx prefix hash: ee0f86e8e0ebaaffbaca64d1badd1180ae06a8d64272cbc1679bccd3b50c5b1a
Tx public key: bc9a92e77f0692c160eaa18a2daeb319a143d73203a83a4322f4cea237f24fd3
Timestamp: 1577793478 Timestamp [UCT]: 2019-12-31 11:57:58 Age [y:d:h:m:s]: 05:038:04:07:10
Block: 35706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177041 RingCT/type: yes/0
Extra: 01bc9a92e77f0692c160eaa18a2daeb319a143d73203a83a4322f4cea237f24fd3021100000030c5b5978f000000000000000000

1 output(s) for total of 467.403600646000 dcy

stealth address amount amount idx
00: e999e050fd03be37be45dfd2f7da7535e92a357b0c9e7401cdc01adc599e9e70 467.403600646000 60281 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": 35716, "vin": [ { "gen": { "height": 35706 } } ], "vout": [ { "amount": 467403600646, "target": { "key": "e999e050fd03be37be45dfd2f7da7535e92a357b0c9e7401cdc01adc599e9e70" } } ], "extra": [ 1, 188, 154, 146, 231, 127, 6, 146, 193, 96, 234, 161, 138, 45, 174, 179, 25, 161, 67, 215, 50, 3, 168, 58, 67, 34, 244, 206, 162, 55, 242, 79, 211, 2, 17, 0, 0, 0, 48, 197, 181, 151, 143, 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