Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a11e46c6ad0b17687da033f648e6571a06bd528a7f8ae0337329f0ae1ef132d6

Tx prefix hash: 6884d5399e58fdec63655c3d96282905cbb4f36cde226a18d533cf61e09a9171
Tx public key: 1c9784cbe04d244c2f2850a72d37806adfe64aa819db7953ee0de83319123748
Timestamp: 1720927399 Timestamp [UCT]: 2024-07-14 03:23:19 Age [y:d:h:m:s]: 00:258:03:29:05
Block: 1065256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184407 RingCT/type: yes/0
Extra: 011c9784cbe04d244c2f2850a72d37806adfe64aa819db7953ee0de8331912374802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2703a69d63aedaea59f4d75b5bcc936b244a18cdbad8cfd7b42f206893f5da1 0.600000000000 1535801 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": 1065266, "vin": [ { "gen": { "height": 1065256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2703a69d63aedaea59f4d75b5bcc936b244a18cdbad8cfd7b42f206893f5da1" } } ], "extra": [ 1, 28, 151, 132, 203, 224, 77, 36, 76, 47, 40, 80, 167, 45, 55, 128, 106, 223, 230, 74, 168, 25, 219, 121, 83, 238, 13, 232, 51, 25, 18, 55, 72, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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