Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3175ae9a61a24d44801ba842980f681144ed349c4f7ce0cda097436d119c22df

Tx prefix hash: 8f1fc33beff1013ce03c360f866dec396fe25e84348e9c6ebc9c9ba05adcf42e
Tx public key: 371b4c8db5212c4fb42024f8d19b72b42284e146a5a44d15caf31249a3edb079
Timestamp: 1684757634 Timestamp [UCT]: 2023-05-22 12:13:54 Age [y:d:h:m:s]: 01:247:01:09:50
Block: 765634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437961 RingCT/type: yes/0
Extra: 01371b4c8db5212c4fb42024f8d19b72b42284e146a5a44d15caf31249a3edb079021100000001b3164c24000000000000000000

1 output(s) for total of 1.782940739000 dcy

stealth address amount amount idx
00: 6bb66f6225d55202ef89c4517667a7b9df97b1332200583005f3961ca0d2147a 1.782940739000 1214631 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": 765644, "vin": [ { "gen": { "height": 765634 } } ], "vout": [ { "amount": 1782940739, "target": { "key": "6bb66f6225d55202ef89c4517667a7b9df97b1332200583005f3961ca0d2147a" } } ], "extra": [ 1, 55, 27, 76, 141, 181, 33, 44, 79, 180, 32, 36, 248, 209, 155, 114, 180, 34, 132, 225, 70, 165, 164, 77, 21, 202, 243, 18, 73, 163, 237, 176, 121, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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