Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2154bdb4be5370459873d36414c71db7513bdd84c9c99f0e84c9875e1f47ad79

Tx prefix hash: 531a72684a4f77cea5cfa8490bf1dde85da33cc3b5d59fa3547189512bb68f53
Tx public key: 82c64b063817215d05761377d9ae6ad9ed6b5c0e36e12c3936a7cd4b581cf318
Timestamp: 1757474216 Timestamp [UCT]: 2025-09-10 03:16:56 Age [y:d:h:m:s]: 00:144:07:56:01
Block: 1365142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103145 RingCT/type: yes/0
Extra: 0182c64b063817215d05761377d9ae6ad9ed6b5c0e36e12c3936a7cd4b581cf318021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e17908fd50b0b03266e94f4289b21a870969c0c7e3516d90e7e1cb751ce6c61b 0.600000000000 1853181 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": 1365152, "vin": [ { "gen": { "height": 1365142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e17908fd50b0b03266e94f4289b21a870969c0c7e3516d90e7e1cb751ce6c61b" } } ], "extra": [ 1, 130, 198, 75, 6, 56, 23, 33, 93, 5, 118, 19, 119, 217, 174, 106, 217, 237, 107, 92, 14, 54, 225, 44, 57, 54, 167, 205, 75, 88, 28, 243, 24, 2, 17, 0, 0, 0, 3, 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