Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec7be6d3df5e21a1a21a36bb8eade4b38b5062b99eb3840b5481af14d668934

Tx prefix hash: f605df0d24cc18f996ca5f73d5c57afc85623c95911c332ba1f149dd054bb54d
Tx public key: 5dcbb29c66416846d4c626bfbbf84901f8bd8086f2fcbc8c44eb6231dfab1d80
Timestamp: 1757356272 Timestamp [UCT]: 2025-09-08 18:31:12 Age [y:d:h:m:s]: 00:146:02:28:40
Block: 1364230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104354 RingCT/type: yes/0
Extra: 015dcbb29c66416846d4c626bfbbf84901f8bd8086f2fcbc8c44eb6231dfab1d8002110000000cad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e6155ef8d4ebdaccac0a0ad27b41d5b80976fbd7a64b3522a30d19ee8e3e48d 0.600000000000 1852269 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": 1364240, "vin": [ { "gen": { "height": 1364230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e6155ef8d4ebdaccac0a0ad27b41d5b80976fbd7a64b3522a30d19ee8e3e48d" } } ], "extra": [ 1, 93, 203, 178, 156, 102, 65, 104, 70, 212, 198, 38, 191, 187, 248, 73, 1, 248, 189, 128, 134, 242, 252, 188, 140, 68, 235, 98, 49, 223, 171, 29, 128, 2, 17, 0, 0, 0, 12, 173, 121, 72, 208, 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