Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4265148622a79bb76f402bbc3b3cc30f995b93eeee34c7f06392c74d05315395

Tx prefix hash: 0bfd3b10b90b0ceab747a0dc6b4d643aeb875e608530196f184b830628544a51
Tx public key: 091ab2b9c8a7dd2f50671efc2fb6f8bacc723a6d2e33f7bf257c4b5881a060ad
Timestamp: 1704909521 Timestamp [UCT]: 2024-01-10 17:58:41 Age [y:d:h:m:s]: 01:071:18:31:05
Block: 932432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312402 RingCT/type: yes/0
Extra: 01091ab2b9c8a7dd2f50671efc2fb6f8bacc723a6d2e33f7bf257c4b5881a060ad02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65a3e65a4c00b2dd18e3f860e3aceb5f759af8f890636e197d0b97f083a3ec31 0.600000000000 1390368 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": 932442, "vin": [ { "gen": { "height": 932432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65a3e65a4c00b2dd18e3f860e3aceb5f759af8f890636e197d0b97f083a3ec31" } } ], "extra": [ 1, 9, 26, 178, 185, 200, 167, 221, 47, 80, 103, 30, 252, 47, 182, 248, 186, 204, 114, 58, 109, 46, 51, 247, 191, 37, 124, 75, 88, 129, 160, 96, 173, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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