Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed7e7e26149a296678c8b6f3532c8017e206563a2637070c92ebf4cf826b66c

Tx prefix hash: 6dab09f7482e28193ef52cd6db3ee5a50d1100d885c2f88d8bbf3053c87b39e6
Tx public key: e5fec1a8cbf6e2b9a0ab0c921496765ed671c4633ce878dc82fa84e7794e67f8
Timestamp: 1711668304 Timestamp [UTC]: 2024-03-28 23:25:04 Age [y:d:h:m:s]: 02:238:09:33:12
Block: 988497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 694997 RingCT/type: yes/0
Extra: 01e5fec1a8cbf6e2b9a0ab0c921496765ed671c4633ce878dc82fa84e7794e67f802110000000a59dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c52eeae1279fb4463ff8ead49eb0a2763fd4aa28f84d5b55353bd408daf307a7 0.000600000000 1448776 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 dinastycoin-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": 988507, "vin": [ { "gen": { "height": 988497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c52eeae1279fb4463ff8ead49eb0a2763fd4aa28f84d5b55353bd408daf307a7" } } ], "extra": [ 1, 229, 254, 193, 168, 203, 246, 226, 185, 160, 171, 12, 146, 20, 150, 118, 94, 214, 113, 196, 99, 60, 232, 120, 220, 130, 250, 132, 231, 121, 78, 103, 248, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: