Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08aa3f150cb2e9b48dd7307533b206b92a7577ea2ff3e36ff1aa3d2a6f83e5a4

Tx prefix hash: 64d9caa748e6124d6ef0b1893e101854ce6c7a2dca2d05c335994383d7c78ef2
Tx public key: f3b71b5fd9a89ef6e9c4cd417ebdea5f1adfebe38d88fd48a579e72e83ac060d
Timestamp: 1712478857 Timestamp [UCT]: 2024-04-07 08:34:17 Age [y:d:h:m:s]: 01:006:18:54:32
Block: 995180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265840 RingCT/type: yes/0
Extra: 01f3b71b5fd9a89ef6e9c4cd417ebdea5f1adfebe38d88fd48a579e72e83ac060d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df53331226b346f838bc0c5d2604343f81c619fd407a33b1ac570ca063a9a98f 0.600000000000 1455586 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": 995190, "vin": [ { "gen": { "height": 995180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df53331226b346f838bc0c5d2604343f81c619fd407a33b1ac570ca063a9a98f" } } ], "extra": [ 1, 243, 183, 27, 95, 217, 168, 158, 246, 233, 196, 205, 65, 126, 189, 234, 95, 26, 223, 235, 227, 141, 136, 253, 72, 165, 121, 231, 46, 131, 172, 6, 13, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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