Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ef1fa28ca0c0c06c585f8bf04f15175a7b18bdcae0706a123643226b649917d

Tx prefix hash: 697fbb9b70e991c8f2d059e75425a2dd2eedaccce9c26d9f4f773ed92920e37c
Tx public key: 69a9ca3f9f6758aab0f7c41ed10323b2f98ab37b0abd833b33b0cdd4664934bc
Timestamp: 1751767668 Timestamp [UCT]: 2025-07-06 02:07:48 Age [y:d:h:m:s]: 00:170:20:41:44
Block: 1319630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120534 RingCT/type: yes/0
Extra: 0169a9ca3f9f6758aab0f7c41ed10323b2f98ab37b0abd833b33b0cdd4664934bc02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c384b868cae690df19a5828da4158161c50dcc4965b6b13dfeae167f34197d3d 0.600000000000 1807323 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": 1319640, "vin": [ { "gen": { "height": 1319630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c384b868cae690df19a5828da4158161c50dcc4965b6b13dfeae167f34197d3d" } } ], "extra": [ 1, 105, 169, 202, 63, 159, 103, 88, 170, 176, 247, 196, 30, 209, 3, 35, 178, 249, 138, 179, 123, 10, 189, 131, 59, 51, 176, 205, 212, 102, 73, 52, 188, 2, 17, 0, 0, 0, 1, 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