Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4938c6a66f5578d9b309bcc001ca06fd61e06f2c10f0befcbe8f815118909eec

Tx prefix hash: 56e47bc7ec52d860a3928e485019b76ffea4888c95044a5c07e8421d76edfc2b
Tx public key: e7a63d3fa1717ce15cb7b85455b3b33bc6b21e3b6cc03b6da8aa26bb75e5806b
Timestamp: 1755103389 Timestamp [UCT]: 2025-08-13 16:43:09 Age [y:d:h:m:s]: 00:099:19:20:00
Block: 1346169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70765 RingCT/type: yes/0
Extra: 01e7a63d3fa1717ce15cb7b85455b3b33bc6b21e3b6cc03b6da8aa26bb75e5806b021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26866b5bb8fbfbf2683d79804e7ef950e3d0b355e1cd7d02ed7fad2ab11bddde 0.600000000000 1834066 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": 1346179, "vin": [ { "gen": { "height": 1346169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26866b5bb8fbfbf2683d79804e7ef950e3d0b355e1cd7d02ed7fad2ab11bddde" } } ], "extra": [ 1, 231, 166, 61, 63, 161, 113, 124, 225, 92, 183, 184, 84, 85, 179, 179, 59, 198, 178, 30, 59, 108, 192, 59, 109, 168, 170, 38, 187, 117, 229, 128, 107, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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