Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b1e40eedd6becd548dec92a07c77399ddbe7f42162499547af2216e6fe3eeea

Tx prefix hash: fef1219ef982b100f10bd9527ea4e23377d821b0e4fab9ba8a6d28be00f8e327
Tx public key: dd5a08a9a8aef6285df695d3397580e3d92bc6b10869ed6b9837895864541acd
Timestamp: 1735188515 Timestamp [UCT]: 2024-12-26 04:48:35 Age [y:d:h:m:s]: 00:089:08:05:13
Block: 1183364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63621 RingCT/type: yes/0
Extra: 01dd5a08a9a8aef6285df695d3397580e3d92bc6b10869ed6b9837895864541acd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a93f6b6f8eaef44b8f521b26ef7ce30bb8b38795f499a40c29c6183672ec97e2 0.600000000000 1669809 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": 1183374, "vin": [ { "gen": { "height": 1183364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a93f6b6f8eaef44b8f521b26ef7ce30bb8b38795f499a40c29c6183672ec97e2" } } ], "extra": [ 1, 221, 90, 8, 169, 168, 174, 246, 40, 93, 246, 149, 211, 57, 117, 128, 227, 217, 43, 198, 177, 8, 105, 237, 107, 152, 55, 137, 88, 100, 84, 26, 205, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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