Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed87d0931c1116e382fd98e25c06ae6ab32777687dd348953a25bbe3eee25f50

Tx prefix hash: 0b25675122eac33463d13543919796463e34e90d1da03707849a307cde674696
Tx public key: ae4d8b8fdbb0e5f7eebd0f72c9e8a63804c9793b64978db1aa3a2bdfef57396f
Timestamp: 1704990335 Timestamp [UCT]: 2024-01-11 16:25:35 Age [y:d:h:m:s]: 01:000:23:35:29
Block: 933111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262016 RingCT/type: yes/0
Extra: 01ae4d8b8fdbb0e5f7eebd0f72c9e8a63804c9793b64978db1aa3a2bdfef57396f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43eaa4e6f170c239b33ff0d0e27ecd4b4c42237af281109783cc42e7ea016555 0.600000000000 1391063 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": 933121, "vin": [ { "gen": { "height": 933111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43eaa4e6f170c239b33ff0d0e27ecd4b4c42237af281109783cc42e7ea016555" } } ], "extra": [ 1, 174, 77, 139, 143, 219, 176, 229, 247, 238, 189, 15, 114, 201, 232, 166, 56, 4, 201, 121, 59, 100, 151, 141, 177, 170, 58, 43, 223, 239, 87, 57, 111, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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