Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84addae540d52d04dd27a193d8c17d4bbc56d38c3383c40144dfc7015fa86447

Tx prefix hash: 019042dbf7f6e77df72cc5a2429764d6dbb22da442838b4cac72bb88fcde09aa
Tx public key: 0c427144f8a4f9ab7507b9387b9498b17abe343ea6486d38d37794ce97cfc9aa
Timestamp: 1720417728 Timestamp [UCT]: 2024-07-08 05:48:48 Age [y:d:h:m:s]: 00:276:10:42:19
Block: 1061013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197521 RingCT/type: yes/0
Extra: 010c427144f8a4f9ab7507b9387b9498b17abe343ea6486d38d37794ce97cfc9aa02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6751b2c189ff46743f2f4c5cbfd9880a117abfcd0a6f0c97293ecaf659b7f5c 0.600000000000 1531504 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": 1061023, "vin": [ { "gen": { "height": 1061013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6751b2c189ff46743f2f4c5cbfd9880a117abfcd0a6f0c97293ecaf659b7f5c" } } ], "extra": [ 1, 12, 66, 113, 68, 248, 164, 249, 171, 117, 7, 185, 56, 123, 148, 152, 177, 122, 190, 52, 62, 166, 72, 109, 56, 211, 119, 148, 206, 151, 207, 201, 170, 2, 17, 0, 0, 0, 8, 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