Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50aed1218686a8e88e0a8f1ae7a306fe4d82065419aa738ef7139806bf0e888c

Tx prefix hash: 1b741c41e8d27a45416742779c6d4e50f2339a63b4dcf7190e9441cd79875cf1
Tx public key: 4bea21e417e8b2c2430c74a946a6f846335033ad2cb7eebed3c64acd27288879
Timestamp: 1745740096 Timestamp [UCT]: 2025-04-27 07:48:16 Age [y:d:h:m:s]: 00:014:09:36:10
Block: 1270439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10297 RingCT/type: yes/0
Extra: 014bea21e417e8b2c2430c74a946a6f846335033ad2cb7eebed3c64acd272888790211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d926643d232a9ea5fea758e191c8b1eb35fdf569364c5fdab91daec193d77abb 0.600000000000 1757682 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": 1270449, "vin": [ { "gen": { "height": 1270439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d926643d232a9ea5fea758e191c8b1eb35fdf569364c5fdab91daec193d77abb" } } ], "extra": [ 1, 75, 234, 33, 228, 23, 232, 178, 194, 67, 12, 116, 169, 70, 166, 248, 70, 51, 80, 51, 173, 44, 183, 238, 190, 211, 198, 74, 205, 39, 40, 136, 121, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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