Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 567b402c08316b3d21cec8e9eb0b9652c8d28bfcfce06e0db6a0bc7531a38f43

Tx prefix hash: 7f4566a81e72163a0d1111b9280aac7314835173025b1e3a2207e00a6f5af487
Tx public key: df1b98c342cbf4c90904b45fe5a1ad7aaa9cc600a7a5d4fcdcd863fe97da9366
Timestamp: 1720310876 Timestamp [UCT]: 2024-07-07 00:07:56 Age [y:d:h:m:s]: 00:271:17:04:52
Block: 1060129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194135 RingCT/type: yes/0
Extra: 01df1b98c342cbf4c90904b45fe5a1ad7aaa9cc600a7a5d4fcdcd863fe97da936602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31aac151d03e55c36c9ab9a54e2ebfb62814f286fecd6791f999de08d2321c74 0.600000000000 1530600 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": 1060139, "vin": [ { "gen": { "height": 1060129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31aac151d03e55c36c9ab9a54e2ebfb62814f286fecd6791f999de08d2321c74" } } ], "extra": [ 1, 223, 27, 152, 195, 66, 203, 244, 201, 9, 4, 180, 95, 229, 161, 173, 122, 170, 156, 198, 0, 167, 165, 212, 252, 220, 216, 99, 254, 151, 218, 147, 102, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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