Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6855304da701d02b4e220aa4dc746f0eb3811da00d83298db3739e11b8c25463

Tx prefix hash: 2c80013388306b0cfc3a9a034a5424c982147911cd3e0385f85eab00d8d5de52
Tx public key: e243ac7c55fdc113a002ebec6cf750367cc5edf753f3d3e1e4303ecfd630d7d1
Timestamp: 1706525903 Timestamp [UCT]: 2024-01-29 10:58:23 Age [y:d:h:m:s]: 00:352:01:51:29
Block: 945827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252067 RingCT/type: yes/0
Extra: 01e243ac7c55fdc113a002ebec6cf750367cc5edf753f3d3e1e4303ecfd630d7d102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2103c825534940272f02bb642b1d4aad24cb3ae8d49b51556e627c141be1a6a 0.600000000000 1404151 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": 945837, "vin": [ { "gen": { "height": 945827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2103c825534940272f02bb642b1d4aad24cb3ae8d49b51556e627c141be1a6a" } } ], "extra": [ 1, 226, 67, 172, 124, 85, 253, 193, 19, 160, 2, 235, 236, 108, 247, 80, 54, 124, 197, 237, 247, 83, 243, 211, 225, 228, 48, 62, 207, 214, 48, 215, 209, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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