Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b938a066a95be977c71c009ad38ab6cb95fb633e365ba3863b723ef63408989

Tx prefix hash: ea4f3ae8bc320148d8ff56f8905bc3b4ae2a5d0eef95781269d30d35406465eb
Tx public key: e09871c70f6e4a1166e52107b2b8e8b595745932340ce39029abde1ab5e681bf
Timestamp: 1699345576 Timestamp [UCT]: 2023-11-07 08:26:16 Age [y:d:h:m:s]: 01:139:01:28:52
Block: 886323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360571 RingCT/type: yes/0
Extra: 01e09871c70f6e4a1166e52107b2b8e8b595745932340ce39029abde1ab5e681bf021100000004faf35c9c000000000000000000

1 output(s) for total of 0.709976500000 dcy

stealth address amount amount idx
00: 0e49a363c531618629a39dbad4c0c0d58138a5a6a2fe1ae6be182ea81e838bce 0.709976500000 1342138 of 0

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": 886333, "vin": [ { "gen": { "height": 886323 } } ], "vout": [ { "amount": 709976500, "target": { "key": "0e49a363c531618629a39dbad4c0c0d58138a5a6a2fe1ae6be182ea81e838bce" } } ], "extra": [ 1, 224, 152, 113, 199, 15, 110, 74, 17, 102, 229, 33, 7, 178, 184, 232, 181, 149, 116, 89, 50, 52, 12, 227, 144, 41, 171, 222, 26, 181, 230, 129, 191, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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