Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d95505fdb0ff05c9fb2bd60c176d6aa0b3d0835b9a8de500ecf99299926135d

Tx prefix hash: 0c14b2eb2885b1c5da83a6f4373b2e05b4b9e50252f1190699b0eac13f468db2
Tx public key: 4e0ea31b2cc2554151877e4fc1833621829ff604a2b4fd73fae74f1bfcd5269c
Timestamp: 1719797207 Timestamp [UCT]: 2024-07-01 01:26:47 Age [y:d:h:m:s]: 01:130:00:56:08
Block: 1055864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351484 RingCT/type: yes/0
Extra: 014e0ea31b2cc2554151877e4fc1833621829ff604a2b4fd73fae74f1bfcd5269c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1def2922b18a8f224b4b789844004fddd7963f1c0393da413ec98fb2fb6453df 0.600000000000 1526269 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": 1055874, "vin": [ { "gen": { "height": 1055864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1def2922b18a8f224b4b789844004fddd7963f1c0393da413ec98fb2fb6453df" } } ], "extra": [ 1, 78, 14, 163, 27, 44, 194, 85, 65, 81, 135, 126, 79, 193, 131, 54, 33, 130, 159, 246, 4, 162, 180, 253, 115, 250, 231, 79, 27, 252, 213, 38, 156, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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