Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a888eda92c93d4b37fde3d3fc9aff04a88932ba0f2ce4081f583d24a299cba

Tx prefix hash: 4211d959a085310f007d5535c8621d44d89b49ba33541ab5db58fe15307dfc89
Tx public key: 58ced7aa44f84a409b1a726e79e20b2f1faf2a1087ad4ed401bcb37e177dcb36
Timestamp: 1763439433 Timestamp [UCT]: 2025-11-18 04:17:13 Age [y:d:h:m:s]: 00:052:01:35:39
Block: 1414564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37283 RingCT/type: yes/0
Extra: 0158ced7aa44f84a409b1a726e79e20b2f1faf2a1087ad4ed401bcb37e177dcb36021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebd1081ffdf1533c1749d2f10b907b94ff1fceba0f835499158a2b0782cfc581 0.600000000000 1903055 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": 1414574, "vin": [ { "gen": { "height": 1414564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebd1081ffdf1533c1749d2f10b907b94ff1fceba0f835499158a2b0782cfc581" } } ], "extra": [ 1, 88, 206, 215, 170, 68, 248, 74, 64, 155, 26, 114, 110, 121, 226, 11, 47, 31, 175, 42, 16, 135, 173, 78, 212, 1, 188, 179, 126, 23, 125, 203, 54, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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