Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0508b37f9fce858a55dc0e5b25508f445aac588cdb629ae0fd7a54bf42195bc1

Tx prefix hash: ba3e3df8ef88275dfa65f59d80e65e67066a0c10c662e787dbcb5ea085d87da9
Tx public key: 84d8ed71e757c704300904e1c743819469b36a4364240c19f9b8afa61c6b7128
Timestamp: 1706504123 Timestamp [UCT]: 2024-01-29 04:55:23 Age [y:d:h:m:s]: 01:137:01:42:17
Block: 945646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359015 RingCT/type: yes/0
Extra: 0184d8ed71e757c704300904e1c743819469b36a4364240c19f9b8afa61c6b71280211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fb0ca7b596edf8c9f1949fffd224fc49d20c8e1e4d4a297ee7665ffd74e1050 0.600000000000 1403962 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": 945656, "vin": [ { "gen": { "height": 945646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fb0ca7b596edf8c9f1949fffd224fc49d20c8e1e4d4a297ee7665ffd74e1050" } } ], "extra": [ 1, 132, 216, 237, 113, 231, 87, 199, 4, 48, 9, 4, 225, 199, 67, 129, 148, 105, 179, 106, 67, 100, 36, 12, 25, 249, 184, 175, 166, 28, 107, 113, 40, 2, 17, 0, 0, 0, 1, 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