Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 305b548de5b717938cb59e1687d8018c43e8b968c69233c911d2d1a44831e248

Tx prefix hash: ed668c79432ee33c600a897f70fbe64afba4853ae060b3ff592e83a48506f60b
Tx public key: 9d51a48e691ad001e8977c6c265846a9b0d5b07e3d83de754f07c6cf79c2d51a
Timestamp: 1714284157 Timestamp [UCT]: 2024-04-28 06:02:37 Age [y:d:h:m:s]: 01:033:21:24:17
Block: 1010158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285192 RingCT/type: yes/0
Extra: 019d51a48e691ad001e8977c6c265846a9b0d5b07e3d83de754f07c6cf79c2d51a0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4b182ec31fa79c0ec0f3cf7a29ec88de867ba1d6869b76b1622a8dd15c34bbb 0.600000000000 1472034 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": 1010168, "vin": [ { "gen": { "height": 1010158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4b182ec31fa79c0ec0f3cf7a29ec88de867ba1d6869b76b1622a8dd15c34bbb" } } ], "extra": [ 1, 157, 81, 164, 142, 105, 26, 208, 1, 232, 151, 124, 108, 38, 88, 70, 169, 176, 213, 176, 126, 61, 131, 222, 117, 79, 7, 198, 207, 121, 194, 213, 26, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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