Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b018afd4bbacd454cd297a35c70fc5ed6b5ef6f7e364da476ab64c164efb7046

Tx prefix hash: 7bca58e62a5a35bf6ba685f960ce71a2d32f4bd4a1de577dc58a25fec22d457c
Tx public key: f1d415ea5bef77a9494e4fe776c73c4e1c52e94abf5d3115d7a0a42687c417e6
Timestamp: 1757274010 Timestamp [UCT]: 2025-09-07 19:40:10 Age [y:d:h:m:s]: 00:081:15:28:00
Block: 1363562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58361 RingCT/type: yes/0
Extra: 01f1d415ea5bef77a9494e4fe776c73c4e1c52e94abf5d3115d7a0a42687c417e6021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf54ce431ea0d39fa70db6d16973132d13349e9ee03888df3041d21ef187420 0.600000000000 1851601 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": 1363572, "vin": [ { "gen": { "height": 1363562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf54ce431ea0d39fa70db6d16973132d13349e9ee03888df3041d21ef187420" } } ], "extra": [ 1, 241, 212, 21, 234, 91, 239, 119, 169, 73, 78, 79, 231, 118, 199, 60, 78, 28, 82, 233, 74, 191, 93, 49, 21, 215, 160, 164, 38, 135, 196, 23, 230, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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