Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44dff03a6223d5474cbe57a51164800440c0e53a630fd056e70932206831202b

Tx prefix hash: 32448808d487a4f2069de47b7a82cf54f9f7ba598a5967f067fa5ebbdfe014b5
Tx public key: 8e576a397a401132c4dc0fb8ba7d0d6ceafbaf2ff849eaf5f88025dabb3c9e7c
Timestamp: 1717799129 Timestamp [UCT]: 2024-06-07 22:25:29 Age [y:d:h:m:s]: 00:281:00:52:51
Block: 1039306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200867 RingCT/type: yes/0
Extra: 018e576a397a401132c4dc0fb8ba7d0d6ceafbaf2ff849eaf5f88025dabb3c9e7c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1270a973705d4cabfcc3437a614f67e81eebda5484b4a14a9a229ceae78946ae 0.600000000000 1507939 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": 1039316, "vin": [ { "gen": { "height": 1039306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1270a973705d4cabfcc3437a614f67e81eebda5484b4a14a9a229ceae78946ae" } } ], "extra": [ 1, 142, 87, 106, 57, 122, 64, 17, 50, 196, 220, 15, 184, 186, 125, 13, 108, 234, 251, 175, 47, 248, 73, 234, 245, 248, 128, 37, 218, 187, 60, 158, 124, 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