Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d9988954843c6f5b1593587d4d9183c4e80b7fba68a7003979902ae6bb66153

Tx prefix hash: 92f0dfd5a2f3a302620b1da7c9717c5ca59bf51655ea16c23cfff39c368d2987
Tx public key: 517a7ec4bbd5d5ed28cf0cce68bdd4b54626af85d304878ad7c965045be52a6c
Timestamp: 1702692941 Timestamp [UCT]: 2023-12-16 02:15:41 Age [y:d:h:m:s]: 01:036:09:51:57
Block: 914067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287340 RingCT/type: yes/0
Extra: 01517a7ec4bbd5d5ed28cf0cce68bdd4b54626af85d304878ad7c965045be52a6c021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1649557fe2e1ee4f8fb97ea42cde16a97079de8b093ebfc60d4227afb49e824 0.600000000000 1371349 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": 914077, "vin": [ { "gen": { "height": 914067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1649557fe2e1ee4f8fb97ea42cde16a97079de8b093ebfc60d4227afb49e824" } } ], "extra": [ 1, 81, 122, 126, 196, 187, 213, 213, 237, 40, 207, 12, 206, 104, 189, 212, 181, 70, 38, 175, 133, 211, 4, 135, 138, 215, 201, 101, 4, 91, 229, 42, 108, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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