Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556082d175bd08c997cebdf5611d832876137a72dfb7dc97dbcbb6b6399f5a16

Tx prefix hash: b86755a455b080540b54e53045a92799a6479acdd6228f975adc8b67edda2ea0
Tx public key: 5527e87276f8c87dac6e7068d637c3e5d1553aa630d987c5d12cfa94eef390ef
Timestamp: 1718578341 Timestamp [UCT]: 2024-06-16 22:52:21 Age [y:d:h:m:s]: 00:221:15:57:58
Block: 1045782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158569 RingCT/type: yes/0
Extra: 015527e87276f8c87dac6e7068d637c3e5d1553aa630d987c5d12cfa94eef390ef0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3069689c69d0df1437f48e746778cad1b5b40fd3570687de8cccd424e905bf 0.600000000000 1515453 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": 1045792, "vin": [ { "gen": { "height": 1045782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3069689c69d0df1437f48e746778cad1b5b40fd3570687de8cccd424e905bf" } } ], "extra": [ 1, 85, 39, 232, 114, 118, 248, 200, 125, 172, 110, 112, 104, 214, 55, 195, 229, 209, 85, 58, 166, 48, 217, 135, 197, 209, 44, 250, 148, 238, 243, 144, 239, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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