Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340a3bc523d4d73459a9fef24d18996302ca0fc8344e299cdb2efaaf08bae348

Tx prefix hash: 2f2dd6f2f1f44c5a8ae3a4029af6d2ec551cb8533dea86a90ab878a501ec07d9
Tx public key: 0509a9cc2679cf446513f19f85d6c4fba140a750246d38f0cb96ebc33569c82a
Timestamp: 1738819066 Timestamp [UCT]: 2025-02-06 05:17:46 Age [y:d:h:m:s]: 00:286:08:54:48
Block: 1213142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202429 RingCT/type: yes/0
Extra: 010509a9cc2679cf446513f19f85d6c4fba140a750246d38f0cb96ebc33569c82a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0013afea178df1fba54cb2be849e57edbc59d1b0aaae19237e4e81a3f17de795 0.600000000000 1699919 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": 1213152, "vin": [ { "gen": { "height": 1213142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0013afea178df1fba54cb2be849e57edbc59d1b0aaae19237e4e81a3f17de795" } } ], "extra": [ 1, 5, 9, 169, 204, 38, 121, 207, 68, 101, 19, 241, 159, 133, 214, 196, 251, 161, 64, 167, 80, 36, 109, 56, 240, 203, 150, 235, 195, 53, 105, 200, 42, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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