Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f38e5e23da3324d23dd20a4f0a9a6b7dcda0a08b27ed05208d29da1d0784cf25

Tx prefix hash: 651ee612c4e164bbc6eb6299d3fb24cbfd28673162bac5361e8c292c64b51791
Tx public key: c9c30aa505572a90e8c3cb3de976a3c90c0ea67579074ea1f37eba1dd997b835
Timestamp: 1672891389 Timestamp [UCT]: 2023-01-05 04:03:09 Age [y:d:h:m:s]: 02:010:18:56:57
Block: 667852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529631 RingCT/type: yes/0
Extra: 01c9c30aa505572a90e8c3cb3de976a3c90c0ea67579074ea1f37eba1dd997b83502110000000152542ceb000000000000000000

1 output(s) for total of 3.759490968000 dcy

stealth address amount amount idx
00: 75899fb1475083a6c88539d49a2aea462e2708682c1f766ea5a1db75272c5ee1 3.759490968000 1109071 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": 667862, "vin": [ { "gen": { "height": 667852 } } ], "vout": [ { "amount": 3759490968, "target": { "key": "75899fb1475083a6c88539d49a2aea462e2708682c1f766ea5a1db75272c5ee1" } } ], "extra": [ 1, 201, 195, 10, 165, 5, 87, 42, 144, 232, 195, 203, 61, 233, 118, 163, 201, 12, 14, 166, 117, 121, 7, 78, 161, 243, 126, 186, 29, 217, 151, 184, 53, 2, 17, 0, 0, 0, 1, 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