Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 058d04eedfe3a58fa862879d7d1070f63a5666775e38db30e3ae3d2eb6353016

Tx prefix hash: dcfaaf5f7797f3f7187cbc437a06c5ff2abea38e7f13ddaa44939cc231893660
Tx public key: 9c5d3cbfd7e1889dfc3ad2c456a04e31c0f870a22a349d33cf731159ee8072f4
Timestamp: 1705821728 Timestamp [UCT]: 2024-01-21 07:22:08 Age [y:d:h:m:s]: 01:002:22:11:17
Block: 939973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263389 RingCT/type: yes/0
Extra: 019c5d3cbfd7e1889dfc3ad2c456a04e31c0f870a22a349d33cf731159ee8072f402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a107cccab393a274ffefe1b81e83140e095d4807f5262a694a5767f7f4e93a3 0.600000000000 1398107 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": 939983, "vin": [ { "gen": { "height": 939973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a107cccab393a274ffefe1b81e83140e095d4807f5262a694a5767f7f4e93a3" } } ], "extra": [ 1, 156, 93, 60, 191, 215, 225, 136, 157, 252, 58, 210, 196, 86, 160, 78, 49, 192, 248, 112, 162, 42, 52, 157, 51, 207, 115, 17, 89, 238, 128, 114, 244, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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