Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54e9b8568788439349651fff7b0607eb2fac6939daeccfad9d895504d1468f02

Tx prefix hash: bd583b7e815d417e399c6a5c602f03c3237fa7c9952158247f5d59f29646cc81
Tx public key: 16f81d1dc9aedd3e1ea953ec780dd6d8191dffd620da662702d5aa60a99dbcba
Timestamp: 1705797439 Timestamp [UCT]: 2024-01-21 00:37:19 Age [y:d:h:m:s]: 01:070:19:26:03
Block: 939774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311715 RingCT/type: yes/0
Extra: 0116f81d1dc9aedd3e1ea953ec780dd6d8191dffd620da662702d5aa60a99dbcba0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f5786c384a94a86ea2e950356c5c0d362b5afc470d41e18d9404f41e36931a 0.600000000000 1397906 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": 939784, "vin": [ { "gen": { "height": 939774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f5786c384a94a86ea2e950356c5c0d362b5afc470d41e18d9404f41e36931a" } } ], "extra": [ 1, 22, 248, 29, 29, 201, 174, 221, 62, 30, 169, 83, 236, 120, 13, 214, 216, 25, 29, 255, 214, 32, 218, 102, 39, 2, 213, 170, 96, 169, 157, 188, 186, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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