Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b8384d1174d6f20581776ca3bcd856cc45c69a751c91227cf877b2ecfdde69

Tx prefix hash: e5b605a5498e44d51a3b02911e5f8a7dc316c4d9f68322626c4d238bc74d7892
Tx public key: de76772f8d6ee30e95e121ae91b8c8dc7ddd40ba607be082aedd3bed02beae62
Timestamp: 1716395131 Timestamp [UCT]: 2024-05-22 16:25:31 Age [y:d:h:m:s]: 00:228:15:36:00
Block: 1027665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163667 RingCT/type: yes/0
Extra: 01de76772f8d6ee30e95e121ae91b8c8dc7ddd40ba607be082aedd3bed02beae6202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd9c6a09b968bc187eaf175b09e1aef21dcedcdba6da4b0f93fac4d815730874 0.600000000000 1495408 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": 1027675, "vin": [ { "gen": { "height": 1027665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd9c6a09b968bc187eaf175b09e1aef21dcedcdba6da4b0f93fac4d815730874" } } ], "extra": [ 1, 222, 118, 119, 47, 141, 110, 227, 14, 149, 225, 33, 174, 145, 184, 200, 220, 125, 221, 64, 186, 96, 123, 224, 130, 174, 221, 59, 237, 2, 190, 174, 98, 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