Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74acf6264198e851d1d117cb1d2bb47771d0e584ed5ffd892ea1b35682cb2ec5

Tx prefix hash: 9b11fd9aaa53f2a6353fa169ac1d9e13fdbd5188edd801cdac928b9aaf700929
Tx public key: 26029f060e66a54c429ce5c0d1d29b7f344923754232a77b74f7153635d16fb8
Timestamp: 1745881115 Timestamp [UCT]: 2025-04-28 22:58:35 Age [y:d:h:m:s]: 00:206:10:41:23
Block: 1271610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145250 RingCT/type: yes/0
Extra: 0126029f060e66a54c429ce5c0d1d29b7f344923754232a77b74f7153635d16fb80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a052f662087b3865e06c221d3dcf372da181bf4df166614eba3c24f9e5de3f2 0.600000000000 1758875 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": 1271620, "vin": [ { "gen": { "height": 1271610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a052f662087b3865e06c221d3dcf372da181bf4df166614eba3c24f9e5de3f2" } } ], "extra": [ 1, 38, 2, 159, 6, 14, 102, 165, 76, 66, 156, 229, 192, 209, 210, 155, 127, 52, 73, 35, 117, 66, 50, 167, 123, 116, 247, 21, 54, 53, 209, 111, 184, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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