Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044072b92e46fda1858a79a2a08820040222838c91e88f7ca43def0c2f781bec

Tx prefix hash: fe39291c3a170ce92ae9630118c43d13719269f8c25cea6aba4f28223df1af3c
Tx public key: 6511c804003d7d34b32d7359a8378ef13dfccbcc7b695c4511f82c043b76e6b5
Timestamp: 1713336179 Timestamp [UCT]: 2024-04-17 06:42:59 Age [y:d:h:m:s]: 01:059:21:21:14
Block: 1002299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303694 RingCT/type: yes/0
Extra: 016511c804003d7d34b32d7359a8378ef13dfccbcc7b695c4511f82c043b76e6b502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b46bcff4d9660e46917a7382d99500d2ad1166fc0626b04fb07ea634e535d1f 0.600000000000 1462815 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": 1002309, "vin": [ { "gen": { "height": 1002299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b46bcff4d9660e46917a7382d99500d2ad1166fc0626b04fb07ea634e535d1f" } } ], "extra": [ 1, 101, 17, 200, 4, 0, 61, 125, 52, 179, 45, 115, 89, 168, 55, 142, 241, 61, 252, 203, 204, 123, 105, 92, 69, 17, 248, 44, 4, 59, 118, 230, 181, 2, 17, 0, 0, 0, 3, 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