Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a5eb9e53d5e86bcc7724017391f5c4ee579a11fe36bc7976f8be02cd3e70b3e

Tx prefix hash: bb68d060ae73af693c060fe4cba51e2b20709c3852dc54f3abfe70a2ac833e04
Tx public key: 84ede8c1f7a4986d740b66f92232950def021793ef5067ac4acc6e994f90b3cd
Timestamp: 1725897307 Timestamp [UCT]: 2024-09-09 15:55:07 Age [y:d:h:m:s]: 00:246:06:33:52
Block: 1106448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175873 RingCT/type: yes/0
Extra: 0184ede8c1f7a4986d740b66f92232950def021793ef5067ac4acc6e994f90b3cd02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6beb0e05906650dc0a96322986e2c796863b9996a9b490063d459d89c2a0a7b0 0.600000000000 1584047 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": 1106458, "vin": [ { "gen": { "height": 1106448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6beb0e05906650dc0a96322986e2c796863b9996a9b490063d459d89c2a0a7b0" } } ], "extra": [ 1, 132, 237, 232, 193, 247, 164, 152, 109, 116, 11, 102, 249, 34, 50, 149, 13, 239, 2, 23, 147, 239, 80, 103, 172, 74, 204, 110, 153, 79, 144, 179, 205, 2, 17, 0, 0, 0, 4, 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