Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1acca14661af66f419f2ec6b69be4ca2daceca49bc9caa0965a0dce9f9737f85

Tx prefix hash: 2476adc9316259bbd29df910b6ac9a2b8b309b05aa8ec820c304c17cc9b815c5
Tx public key: c7c4259049fdc895fd6c2028e8465aab68b662c4b232efb43cf3d30463ecc2ab
Timestamp: 1674401634 Timestamp [UCT]: 2023-01-22 15:33:54 Age [y:d:h:m:s]: 02:098:07:27:15
Block: 680398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591920 RingCT/type: yes/0
Extra: 01c7c4259049fdc895fd6c2028e8465aab68b662c4b232efb43cf3d30463ecc2ab021100000001272bcc39000000000000000000

1 output(s) for total of 3.416322973000 dcy

stealth address amount amount idx
00: 2a6fca75e45384c06d8ad854043f85581d7988e221e8ad891433eb1b32b1c1ff 3.416322973000 1122435 of 0

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": 680408, "vin": [ { "gen": { "height": 680398 } } ], "vout": [ { "amount": 3416322973, "target": { "key": "2a6fca75e45384c06d8ad854043f85581d7988e221e8ad891433eb1b32b1c1ff" } } ], "extra": [ 1, 199, 196, 37, 144, 73, 253, 200, 149, 253, 108, 32, 40, 232, 70, 90, 171, 104, 182, 98, 196, 178, 50, 239, 180, 60, 243, 211, 4, 99, 236, 194, 171, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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