Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee57b60a80bb04e69d752592aeb2bb50d6701bbb3fedac1ca57fd855dd020db5

Tx prefix hash: 240a00bafea1670b9821b01fc2bc45a060837dc2479e2094a6bc1b383102dbff
Tx public key: 98bc34e213f8f5e0ae73fb33194288f95b601fdd84027cb0fb85da6ab39a2d87
Timestamp: 1729528407 Timestamp [UCT]: 2024-10-21 16:33:27 Age [y:d:h:m:s]: 00:190:19:44:24
Block: 1136502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136219 RingCT/type: yes/0
Extra: 0198bc34e213f8f5e0ae73fb33194288f95b601fdd84027cb0fb85da6ab39a2d870211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31620d48eba4e0b663156ce64c4bbca87c3d1b571d7a2e8c6b6cc3fdfe3bd141 0.600000000000 1619847 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": 1136512, "vin": [ { "gen": { "height": 1136502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31620d48eba4e0b663156ce64c4bbca87c3d1b571d7a2e8c6b6cc3fdfe3bd141" } } ], "extra": [ 1, 152, 188, 52, 226, 19, 248, 245, 224, 174, 115, 251, 51, 25, 66, 136, 249, 91, 96, 31, 221, 132, 2, 124, 176, 251, 133, 218, 106, 179, 154, 45, 135, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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