Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367a6b2c29b464010ba42c76056bd43152fbede9bccbc7ccbd9d2371b70aba27

Tx prefix hash: 1d5dbdb79d08637063d9aeb8f5b53b9fd96c4ca08e4917fe1115a508840ec191
Tx public key: dcb14b599563beacda458509e726b4a7bd98caa9dc33858e79e42ef02d57e824
Timestamp: 1672591387 Timestamp [UCT]: 2023-01-01 16:43:07 Age [y:d:h:m:s]: 02:281:07:28:44
Block: 665377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720422 RingCT/type: yes/0
Extra: 01dcb14b599563beacda458509e726b4a7bd98caa9dc33858e79e42ef02d57e82402110000000252542ceb000000000000000000

1 output(s) for total of 3.831155255000 dcy

stealth address amount amount idx
00: 704d8de88be46208309c89e411014e1152fa5e427c90f7205c6232425f01262c 3.831155255000 1106418 of 0

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": 665387, "vin": [ { "gen": { "height": 665377 } } ], "vout": [ { "amount": 3831155255, "target": { "key": "704d8de88be46208309c89e411014e1152fa5e427c90f7205c6232425f01262c" } } ], "extra": [ 1, 220, 177, 75, 89, 149, 99, 190, 172, 218, 69, 133, 9, 231, 38, 180, 167, 189, 152, 202, 169, 220, 51, 133, 142, 121, 228, 46, 240, 45, 87, 232, 36, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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