Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e0df7703aaa21b88c5421cc5ed969c44990ba7ea67886326f36acdac2e83d16

Tx prefix hash: a6a2af3055137f7535fe35a74fb792348ecc2aefe78c9eb5b1c14ca4a7710888
Tx public key: 8f43a7aa8e35b2b7ee42e95436216a6467740303693edee7803950a4d4a474b2
Timestamp: 1695826871 Timestamp [UCT]: 2023-09-27 15:01:11 Age [y:d:h:m:s]: 01:210:16:58:09
Block: 857348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411667 RingCT/type: yes/0
Extra: 018f43a7aa8e35b2b7ee42e95436216a6467740303693edee7803950a4d4a474b2021100000005faf35c9c000000000000000000

1 output(s) for total of 0.885625718000 dcy

stealth address amount amount idx
00: aba0065b1780c51b7b51306fb5f78a29f31847f267b835e3da96258fd215206d 0.885625718000 1311464 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": 857358, "vin": [ { "gen": { "height": 857348 } } ], "vout": [ { "amount": 885625718, "target": { "key": "aba0065b1780c51b7b51306fb5f78a29f31847f267b835e3da96258fd215206d" } } ], "extra": [ 1, 143, 67, 167, 170, 142, 53, 178, 183, 238, 66, 233, 84, 54, 33, 106, 100, 103, 116, 3, 3, 105, 62, 222, 231, 128, 57, 80, 164, 212, 164, 116, 178, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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