Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971229a5eaf6958e7fe7ca8f8a610ef6bf793abc6c0ed69db0d4a05cf5dd3155

Tx prefix hash: c7a52730ac51ab656b612b80a74fa309edfd5ef07cc5d844b3bab354826bd65a
Tx public key: c84605a9ad3300f2e5e9b855c547380bab8e991918ce52d61f529f1a8d843e9e
Timestamp: 1717962500 Timestamp [UCT]: 2024-06-09 19:48:20 Age [y:d:h:m:s]: 00:292:16:43:01
Block: 1040661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209174 RingCT/type: yes/0
Extra: 01c84605a9ad3300f2e5e9b855c547380bab8e991918ce52d61f529f1a8d843e9e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51ec302ba37794e200b47c0f19a602a38ac03ddf57ce028c9770398dcb9ddc9d 0.600000000000 1509318 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": 1040671, "vin": [ { "gen": { "height": 1040661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51ec302ba37794e200b47c0f19a602a38ac03ddf57ce028c9770398dcb9ddc9d" } } ], "extra": [ 1, 200, 70, 5, 169, 173, 51, 0, 242, 229, 233, 184, 85, 197, 71, 56, 11, 171, 142, 153, 25, 24, 206, 82, 214, 31, 82, 159, 26, 141, 132, 62, 158, 2, 17, 0, 0, 0, 3, 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