Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf0ca286fb93b5b7d9388b2d897b2702d5e99c2112c475b807fafb57a686941a

Tx prefix hash: d111f3749aa2daf85f910e7831859716815f491362954e391305e3a003884c1f
Tx public key: 277ba50a7afe92fd4c73c09362ca419be5f86a2ec3a423d68e2111da26e7630f
Timestamp: 1761879907 Timestamp [UCT]: 2025-10-31 03:05:07 Age [y:d:h:m:s]: 00:006:19:10:27
Block: 1401653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4852 RingCT/type: yes/0
Extra: 01277ba50a7afe92fd4c73c09362ca419be5f86a2ec3a423d68e2111da26e7630f02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a25d70073068e53c12718e884dded314f98dd9da9e0385c90b6cd54922f6acb5 0.600000000000 1889972 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": 1401663, "vin": [ { "gen": { "height": 1401653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a25d70073068e53c12718e884dded314f98dd9da9e0385c90b6cd54922f6acb5" } } ], "extra": [ 1, 39, 123, 165, 10, 122, 254, 146, 253, 76, 115, 192, 147, 98, 202, 65, 155, 229, 248, 106, 46, 195, 164, 35, 214, 142, 33, 17, 218, 38, 231, 99, 15, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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